*************************************************** ** NP00647 FILE ** ** DATE = 01/20/98 ** PHONE = 8-444-0017 ** CONTACT = SANDY PETERSON ** C/T = RD0011 ** USER = SANDYPE NODE = RALVM29 ** *************************************************** APARTXT NA03426 = When a remote physical port got hung, DLSw should be able to detect the condition and disconnect the session and then re-establish a new one as a backup. DLSw fails to do so causing the traffic stop. APARTXT NA03297 = The algorithm to compute whether an LSA is more recent is incorrect when the checksums are different. APARTXT NA03296 = One can get a core dump if_conf_close() when a PPP or frame relay link goes up and down rapidly. APARTXT NA03285 = ospf_nh_find: FAILED! message on F/R NBMA mesh network APARTXT NA03333 = On machines that have been running for more than 248 days, the command vmstat fails with a fatal error message APARTXT NA03334 = required for build APARTXT NA03335 = Internal Enhancements APARTXT NA03331 = DHCP server uses PING option before sending DHCP reply. This option is not standard. APARTXT NA03363 = When you execute the command serialport,it fails with an error message as follows: /usr/bin/serialport-526: rshexit not found APARTXT NA03389 = Under certain conditions, gated does not install the alternet F/R route when the primary F/R route goes down. APARTXT NA03446 = Internal Enhancements for NP00647 APARTXT NA03453 = Frame P2P address should be marked down by default. It will be marked up when the DLCI comes up. APARTXT NA03468 = This defect also includes a change to keep the end of a PPP or P2P frame relay interface from being advertised until the neighbor relationship is FULL. This is to accommodate Fuji Bank's network summary design. ENDSET COMPID FOR PTF NP00647 = 564801600,140 PRODID FOR PTF NP00647 = 5648016,Multiprotocol Network Program PREREQ FOR NP00647 = NONE ENDSET COREQ FOR NP00647 = NONE ENDSET SUP FOR NP00647 = NONE ENDSET IFREQ FOR NP00647 = NONE ENDSET MEMO TO USERS = +---------------------------------------------------------------+ | | | MEMO FOR NP00647 | | | +---------------------------------------------------------------+ CONTENTS OF THIS MEMO _____________________ o Description of Supersede and Prerequisite PTFs o Installation instructions for NP00647 o Engineering PTFs with contents included in Production PTFs SUPERSEDE AND PREREQUISITE PTFS ________________________________ NP00647 is not a supersede PTF. There are no prerequisite PTFs for NP00647. Any user at base V1R4 can apply this ptf. Having PTFs NP00620, NP00623, NP00625, NP00627, NP00629, NP00640, NP00642, NP00644, NP00645, NP00646 though not required, will not prevent NP00647 from being applied. All the fixes contained in NP00646,NP00645, NP00644, NP00642, NP00640, NP00629, NP00627, NP00625, NP00623 and NP00620 are contained in NP00647. Users at any release levels other than V1R4 must migrate to that level (using NP99933, NP99932 or NP99931) and be committed at that level before applying NP00647. Note: NP99933 is an MES Upgrade to V1R4 at PTF level NP00644. NP99932 is an MES Upgrade to V1R4 at PTF level NP00625. NP99931 is an MES Upgrade to V1R4 base. PTF INSTALL INSTRUCTIONS FOR NP00647 ____________________________________ Potential problems or delays in the installation procedure can be avoided if you perform certain actions first. CLEANING UP THE 6611 TRANSFER DIRECTORY Receiving installation files places them in the transfer directory of the 6611. If you know you have unnecessary files in the transfer directory (such as outdated dumps or reports), delete the files before beginning the installation. Refer to "Delete Transfer Directory Files" in the Operations chapter of the IBM Multiprotocol Network Program Operations and Problem Management manual for details. STOPPING TRACES Before beginning the installation process for any update, stop all trace activities. Active traces might cause installation to fail because of insufficient space. Refer to the Problem Determination chapter of the IBM Multiprotocol Network Program Operations and Problem Management manual for information on stopping traces. In particular, it is important that IP routing (gated) protocol traces should be stopped before installing this PTF. HANDLING DEVELOPMENT PTFS Before beginning the installation process for any software update, check to see if you have any development PTFs on your system. Development PTFs may be identified as containing the characters FX in their names, for example: Name: mpnp.obj NP00001 ---------------------- Fix ID Release ---------------------- FX00001 01.01.0000.0001 If you know that you have development PTFs on your system, call your IBM Support Center and provide the following information: o The development PTFs that are already on your system o The software updates you wish to install INSTALLING SOFTWARE UPDATES Software updates are installed from the transfer directory using the Software Installation and Maintenance Facility of the Multiprotocol Network Program V1R3 Supplement(SD35-0238). This is a multiphase process that permits the software updates to be tested before making them a permanent part of the Multiprotocol Network Program. When updating software, the first step after importing the software update is to apply the software update. After a software update is applied to a 6611, it can be activated at a later time. You can specify the maintenance level and the date and time of the activation. The 6611 will be re-IPLed at activation time. Thus, the application of a PTF is not directly coupled with the re-IPL of the router. Any software update that is applied, but not activated in the currently running 6611, can be rejected at any time. A software update must be active before it can be committed. Warning: When you commit the software update, the change is permanent. There are several rules to consider when installing software updates that have dependencies: o Software updates cannot be applied until their prerequisite software updates have been applied. o Applied software updates cannot be committed until their prerequisite software updates have been committed. Possible Messages When Applying PTFs: If there is not sufficient space available, you will see a system message similar to: Installation failed. Please press enter to view the detailed information. (Assuming Enter is pressed, this detailed message is displayed:) installp could not complete because there is not enough space in file system /usr. It needs 476 more 1K blocks. The space available in /usr is less than the minimum required for this operation. The selected install operation will not be started now. Press Enter to continue. If there are more than 1000 1K blocks free in each file system, then you will see different messages depending on whether there was sufficient room for the PTFs you selected to apply. NOTE: If you have insufficient space in the file systems other than /tmp and you have commited all prior PTF's, you must contact IBM service. IBM service will make the appropriate adjustments to the file systems. If you select multiple PTFs to be applied and there is room for some, but not all, only the ones that fit will be applied. The log file pd_update.log in the transfer directory will inform you of this. To perform software updates from the System Manager: 1. Log in to the System Manager using a controlling user ID. 2. Select Software Installation and Maintenance on the System Manager main menu. Follow this procedure to install your software update using the System Manager: Step 1 Your software update is sent to you on diskettes or tape. The software update must be moved to the transfer directory for installation. Before proceeding, refer to "Recommended Software Pre-Installation Actions" for suggested actions if you have not already done so. Step 2 Select Receive Software Updates from the Software Installation and Maintenance menu to move the update files to the transfer directory in the 6611. These import methods are available: * FTP * Modem * Tape * Diskette Before receiving any software files, the system validates that enough space is available in the transfer directory. NOTE: Steps 3 and 4 are optional steps for informational purposes only and are not required for this installation Step 3 Select List Software Updates in the Transfer Directory to view a list of the software in the transfer directory of the 6611, Step 4 Select List All Problems Fixed by Software Updates to list the problems fixed by the software updates in the transfer directory. Step 5 Select Apply Software Updates to install the software updates on the 6611. The installation ends without a re-ipl, and you are returned to the Software Installation Maintenance menu. Step 6 Select Activate Applied Software Updates to activate the applied software updates. In the first selection screen, select NP00647. In the second selector screen you must use "none" as a selection if that is the only choice or if you wish to select no EPTF's. COMMITTING THE SOFTWARE UPDATE (PTF NP00647) CAUTION: When you commit the software update, the change is permanent. You will not be able to reverse the commit. When PTF NP00647 is committed, underlying PTFs are committed also. All EPTFs(FX....) are rejected when NP00647 is committed. Step 1 Select Commit Active Software Updates to commit the activated software updates. Refer to Chapter 5 "Software Installation and Maintenance" in the Multiprotocol Network Program Supplement Version 1 Release 3 (SD35-0238) more installation information. ------------------------------------------------------------ Installation of PTF NP00647 along with the prerequisite and corequisite PTF's, will alleviate the need for the engineering PTF's listed below to reside on your machine. NOTE: If you are currently running with an Engineering PTF that is not on the list below, contact your IBM Service representative for possible additional instructions. FX62001 FX62002 FX62301 FX62302 FX62303 FX62501 FX62502 FX64001 FX64201 FX64202 FX64203 FX64401 FX64402 FX64403 FX64501 FX64502 FX64601 FX64602 FX64603 END OF MEMO - NP00647 ENDSET LABELTXT Selective Fix Package For use on MPNP V1, R4.0 only ENDSET ***************************************************